Skip to content

Conversation

@Eliaaazzz
Copy link
Contributor

@Eliaaazzz Eliaaazzz commented Jan 14, 2026

Description

Fixes #37289 : Replaces direct access to the internal _type_hints attribute with the public get_type_hints() accessor in ExternalTransform.expand().

Why this is needed

Directly accessing self._type_hints causes an AttributeError if the type hints have not been explicitly initialized before the expansion phase. This issue was observed specifically when using StorageWriteToBigQuery with with_auto_sharding=True, which triggers an ExternalTransform expansion where _type_hints is missing.

Using get_type_hints() is the correct, defensive approach as it ensures valid type hints (or an empty instance) are returned, preventing the crash.

Testing

  • Reproduced the crash locally using a script involving StorageWriteToBigQuery with auto-sharding enabled.
  • Verified that the fix resolves the AttributeError and allows the pipeline to proceed past the expansion phase.

Checklist

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Eliaaazzz, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical AttributeError that could arise during the expansion phase of ExternalTransform when the internal _type_hints attribute was accessed before its initialization. By adopting the more robust get_type_hints() method, the system now defensively retrieves type hints, ensuring pipeline stability and preventing crashes in scenarios where type hints might be absent or not yet set up, thereby improving the reliability of data processing operations.

Highlights

  • AttributeError Fix: Replaced direct access to the internal self._type_hints attribute with the public self.get_type_hints() method within ExternalTransform.expand(). This change prevents an AttributeError that occurred when _type_hints was not explicitly initialized, particularly impacting StorageWriteToBigQuery with auto-sharding.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@codecov
Copy link

codecov bot commented Jan 14, 2026

Codecov Report

❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 55.17%. Comparing base (4dcc27d) to head (8fe6cc6).

Files with missing lines Patch % Lines
sdks/python/apache_beam/transforms/external.py 80.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##             master   #37299      +/-   ##
============================================
+ Coverage     55.16%   55.17%   +0.01%     
  Complexity     1676     1676              
============================================
  Files          1068     1068              
  Lines        167257   167342      +85     
  Branches       1208     1208              
============================================
+ Hits          92261    92338      +77     
- Misses        72816    72824       +8     
  Partials       2180     2180              
Flag Coverage Δ
python 80.79% <80.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Contributor

Assigning reviewers:

R: @jrmccluskey for label python.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@Eliaaazzz Eliaaazzz force-pushed the users/Eliaaazzz/fix-issue-37289 branch from 69f022f to e74143d Compare January 14, 2026 07:49
@Eliaaazzz
Copy link
Contributor Author

I have pushed the fix for the linting issue.

Regarding the Python 3.13 failure, it seems unrelated to my changes since the tests for Python 3.10, 3.11, and 3.12 all passed. I also noticed the logs indicate '272 similar failures in the previous 7 days', suggesting this might be a known flaky test in the CI environment.

Could you please take a look?

@Eliaaazzz
Copy link
Contributor Author

Thanks @derrickaw! I've fixed the line length issue in the latest commit. Standing by for the next steps.

@derrickaw
Copy link
Collaborator

Looks like a few more lint issues that need resolving. Make sure to have gone through this to assist - https://github.com/apache/beam/blob/master/contributor-docs/python-tips.md#lint-and-formatting-checks

@github-actions github-actions bot added build and removed build labels Jan 15, 2026
@Eliaaazzz Eliaaazzz force-pushed the users/Eliaaazzz/fix-issue-37289 branch from 33e8676 to 7510d50 Compare January 15, 2026 06:25
@github-actions github-actions bot added build and removed build labels Jan 15, 2026
@Eliaaazzz
Copy link
Contributor Author

Looks like a few more lint issues that need resolving. Make sure to have gone through this to assist - https://github.com/apache/beam/blob/master/contributor-docs/python-tips.md#lint-and-formatting-checks

Hi Derrick, the CI checks are all green now. The previous failure appeared to be a flaky test (infrastructure issue with Socket closed), and it passed successfully after a retry.

Please let me know if there is anything else needed. Thanks!

@derrickaw
Copy link
Collaborator

LGTM - will let @jrmccluskey do final review. Thanks.

@Eliaaazzz
Copy link
Contributor Author

LGTM - will let @jrmccluskey do final review. Thanks.

Thanks for your patience and guidance, appreciate it!

Copy link
Contributor

@jrmccluskey jrmccluskey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Good catch, thanks!

@jrmccluskey jrmccluskey merged commit 68e0d66 into apache:master Jan 15, 2026
101 checks passed
@Eliaaazzz
Copy link
Contributor Author

LGTM. Good catch, thanks!
Thank you for the quick review and for merging this! Glad I could help improve the robustness here. Looking forward to more contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants